fix(ci): resolve new govulncheck advisories (pgx bump + docker exclusions)#163
Conversation
Govulncheck began failing on four newly-published advisories in existing dependencies (unrelated to any code change): - GO-2026-5004 (github.com/jackc/pgx/v5): SQL injection via the non-default simple protocol with dollar-quoted literals. Fixed by upgrading pgx/v5 v5.9.0 -> v5.9.2. - GO-2026-5617 / GO-2026-5668 / GO-2026-5746 (github.com/docker/docker): docker cp / archive host-path issues. docker/docker has no patched release (only moby/moby/v2), so these join the existing docker/docker exclusions in the CI allowlist. Dependency upgrade tracked by #151. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01WnKgCRfMvFcZAkoVbr8k79
|
Warning Review limit reached
Next review available in: 45 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (3)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
2 participants
Summary
Govulncheck started failing across the repo on four newly-published Go advisories in existing dependencies. The workflow runs
govulncheck@latestagainst the live vuln DB, so these began failing on their own (independent of any code change) and affectmainas well. This triages each: fix what's fixable, allowlist what isn't.Changes
github.com/jackc/pgx/v5v5.9.0 → v5.9.2 — fixes GO-2026-5004 (SQL injection via the non-default simple protocol with dollar-quoted literals). This is a real, patched vulnerability, so it's fixed rather than suppressed..github/workflows/engine-ci.yml) — GO-2026-5617, GO-2026-5668, GO-2026-5746 (docker cp/ archive host-path issues).docker/dockerandmoby/mobyhave no patched release (onlymoby/moby/v2is fixed), so these join the existing docker/docker exclusions. The underlying dependency upgrade is tracked by Upgrade github.com/docker/docker to v29 (CVE-2026-34040, CVE-2026-42306) #151.Testing
make test— not affected (no engine logic changed); CI will run itmake lint—go build ./...passes with pgx v5.9.2Related Issues
Relates to #151 (docker/docker upgrade). Unblocks Govulncheck on #162 and other open PRs once merged to
main.Generated by Claude Code